home *** CD-ROM | disk | FTP | other *** search
- Path: ix.netcom.com!netnews
- From: miker3@ix.netcom.com (Mike Rubenstein)
- Newsgroups: comp.lang.c
- Subject: Re: Why does a compiled program fail on another machine?
- Date: Wed, 03 Jan 1996 12:04:47 GMT
- Organization: Netcom
- Message-ID: <30ea6d57.45218688@nntp.ix.netcom.com>
- References: <820634806snz@metsys.demon.co.uk>
- NNTP-Posting-Host: ix-dc8-18.ix.netcom.com
- X-NETCOM-Date: Wed Jan 03 4:04:09 AM PST 1996
- X-Newsreader: Forte Agent .99c/16.141
-
- Douglas John Standen <John@metsys.demon.co.uk> wrote:
-
- |>Having written and run a quite complex program, I find that it
- |>works perfectly on my 386/22 every time, but fails on my friends
- |>486 with acos domain error.
- |>
- |>Is there any good reason why a C compiled program will always run
- |>on its host machine but cause a problem on a non host, if so how
- |>does one locate and correct such an error? Apart from compile it
- |>on the non host machine!
-
- Most likely this is caused by an uninitialized variable that happens
- to take on a legal argument value for acos() on one machine but not
- the other.
-
- Michael M Rubenstein
-